We recommend the user read this documentation and examine the included sample applications to become familiar with the Mail for .NET classes. For the most basic quick-start, create a new Windows Application project in Visual Studio, and see the Code Examples page for accessible examples to try.
PowerTCP Mail for .NET is a complete suite of classes that integrate SMTP, POP, IMAP and RFC 2822 mail message construction into any .NET application. This topic, and related subtopics, address issues such as licensing, distribution, and support for PowerTCP Mail for .NET. For code examples and a programmer's reference of the classes used by the PowerTCP Mail for .NET, see the Assembly Overview section.
Sample | Description |
---|---|
SMTP Client | Create and send Internet email using the MailMessage class and the Smtp component. |
SMTP Web Client | Create and send email from an ASP.NET application. |
POP Client | Get message headers or complete messages from a mail account. Reply to messages or Forward and Redirect them to other recipients. Delete messages from the account. |
POP Web Client | Get messages from an ASP.NET application. |
IMAP Client | Download messages, create and manage remote mailboxes, upload messages and set message flags. |
IMAP Web Client | Get messages and manage remote mailboxes from an ASP.NET application. |
IMAP Part Retriever | Retrieve specific parts of messages (for example, only attachments) from the server. |
Message Editor | Load and display a message for editing. View its various parts (including headers, attachments, and nested parts). Modify the message and save it. |
SMTP Web Service | Create and send email from a web service application. |
SMTP WCF Service | Create and send email from a WCF service. |
SMTP WPF Client | A WPF version of the SMTP Client sample. |
Our mission is to deliver high quality Internet connectivity solutions to Internet application developers. Our goal is to supplement these solutions with timely support resources that can help at many different levels.
You must have an active connection to the Internet to view these links.
Dart installation executables are authenticode signed with a "Dart Communications" digital certificate to ensure against tampering during distribution.
Dart dlls included in the installation bin directory are .NET strong name signed, but not authenticode signed. These dlls are used by the sample applications and typically referenced in users' products.
For those users who require dlls signed by the author company (for example, for Windows logo compliance), dlls that have been signed with the "Dart Communications" digital certificate are also included in the product. These dlls are contained in the "Signed Distributables" sub-folder under the installation bin folder.
In accordance with the End-User Licensing Agreement, pre-compiled Dart dlls may NOT be signed with a user's own certificate. However, for users who wish to independently sign these dlls, Dart offers an ISV license which allow for this. Please contact sales@dart.com for more information.
Target Platforms: Microsoft .NET Framework 2.0 SP1 and higher.